AI assistance: Drafted with AI assistance and edited by Auburn AI editorial.
\n\n
Starting a home lab for the first time is genuinely disorienting – most guides assume you already know what a VLAN is, and the ones aimed at beginners tend to skip the parts that actually trip people up. From our experience, new self-hosters typically arrive with a spare machine, a vague goal, and a browser full of contradictory forum posts pointing in different directions. That gap between “I have old hardware sitting around” and “I have a functioning, organized home lab” is wider than most introductory content admits, and it involves real decisions about networking, software, and how much complexity you actually want to take on. This guide is meant to close that gap without glossing over the parts that make it hard.
\n\n
Key Takeaways
- Every self-hosting setup ever follows the same core pattern: a compute device, storage, a network switch, and software — you do not need expensive gear to start.
- A Raspberry Pi 5 or a used mini PC like the HP EliteDesk 800 G3 is the most practical entry point for beginners, costing under $150.
- A NAS device such as the Synology DS223 gives you centralized file storage with a beginner-friendly interface and RAID redundancy out of the box.
- Your home network is the backbone of your lab — even a basic managed switch like the TP-Link TL-SG108E dramatically improves reliability and control.
- The most common beginner mistake is buying too much hardware too soon; start with one service, get it stable, then expand.
\n\n
\n\n
What Is Self-Hosting and Why Does It Matter?
\n\n
Every selfhosting setup ever starts with the same fundamental idea: instead of relying on a third-party cloud service to store your files, run your apps, or manage your data, you run those services yourself on hardware you own and control. In practical terms, this means replacing Google Photos with your own Nextcloud instance, swapping Spotify for a self-hosted Jellyfin media server, or running your own VPN so you can securely access your home network from anywhere in the world. You own the hardware, you own the data, and you control the uptime.
\n\n
Self-hosting has exploded in popularity over the past several years, and for good reason. Privacy concerns, rising subscription costs, and the sheer satisfaction of running your own infrastructure have drawn hundreds of thousands of people into the home lab hobby. According to community surveys on r/selfhosted, over 60% of self-hosters run at least three separate services simultaneously, and the average home lab grows to include seven or more applications within the first year of operation. Whether you are a complete newcomer or someone who has dabbled but never built a cohesive setup, this guide walks you through everything you need to know.
\n\n
Every Self-Hosting Setup Ever: The Anatomy of a Home Lab
\n\n
In a real home lab setup, there are four core components that appear in virtually every configuration, from a single Raspberry Pi on a shelf to a full 42U server rack in a basement. Understanding these four pillars will help you make smarter purchasing decisions and avoid the trap of buying gear you do not actually need yet.
\n\n
1. Compute
\n
This is the brain of your operation — the device that actually runs your software. It can be as simple as a Raspberry Pi single-board computer, a repurposed old laptop, a used mini PC, a tower server, or a rack-mounted enterprise server. The key specs to pay attention to are CPU core count, RAM capacity, and TDP (thermal design power), which directly affects your electricity bill. A device drawing 10 watts continuously costs roughly $10 to $15 per year to run in most parts of the US, while a full tower server drawing 150 watts can cost over $150 annually.
\n\n
2. Storage
\n
Your data has to live somewhere. Storage in a home lab comes in two main forms: direct-attached storage (drives physically inside your compute device) and network-attached storage, commonly called a NAS. A NAS is a dedicated device designed specifically to store and serve files across your local network, usually with support for RAID arrays that protect your data even if one drive fails.
\n\n
3. Networking
\n
Your home router is almost certainly not enough once you start self-hosting seriously. A managed network switch lets you create VLANs (Virtual Local Area Networks) to isolate your lab traffic from your regular home devices, dramatically improving both security and performance. A basic managed switch with 8 ports is usually the first networking upgrade every home lab enthusiast makes.
\n\n
4. Software Stack
\n
This is where the magic happens. Most self-hosters use Docker containers to run their applications, managed through a tool like Portainer or Docker Compose. A reverse proxy such as Nginx Proxy Manager sits in front of all your services and routes web traffic to the right container. Operating systems like Ubuntu Server, Debian, or TrueNAS provide the foundation everything else runs on.
\n\n
Prerequisites: What You Need Before You Start
\n\n
Before you purchase a single piece of hardware, make sure you have the following in place. Based on community experience, skipping these steps is the number one reason beginners get frustrated and abandon their first build.
\n\n
- \n
- A basic understanding of your home network — know your router’s IP address and how to access its admin panel.
- A free account on a DNS provider such as Cloudflare, which you will use to expose services securely.
- At least 8GB of free space on a USB drive for creating bootable OS installers.
- A dedicated power strip or UPS (Uninterruptible Power Supply) to protect your hardware from power fluctuations.
- Patience — your first setup will break, and that is completely normal and expected.
\n
\n
\n
\n
\n
\n\n
Step-by-Step Walkthrough: Building Your First Setup
\n\n
Step 1: Choose Your Compute Device
\n
For a first build, aim for something with at least 4 CPU cores, 8GB of RAM, and low power draw. A used mini PC in the $80 to $120 range is an excellent starting point. Avoid buying a full rack server as your first machine — the noise, heat, and power consumption will overwhelm a beginner setup.
\n\n
Step 2: Install Your Operating System
\n
Download Ubuntu Server 24.04 LTS (Long Term Support) and flash it to a USB drive using a tool like Balena Etcher. Boot your compute device from the USB and follow the on-screen installer. Choose the minimal install option and enable OpenSSH during setup so you can manage the machine remotely from your regular computer.
\n\n
Step 3: Install Docker and Portainer
\n
Once your OS is running, connect via SSH and install Docker using the official convenience script. Then deploy Portainer, a web-based Docker management interface, as your first container. Portainer runs on port 9443 by default and gives you a visual dashboard to manage all your future containers without touching the command line.
\n\n
Step 4: Deploy Your First Service
\n
What actually works in practice for a first service is something immediately useful — Nextcloud for file syncing, Jellyfin for media streaming, or Home Assistant for smart home automation. Pick one, follow its Docker Compose documentation, and get it running before adding anything else. Resist the urge to deploy ten services at once.
\n\n
Step 5: Set Up a Reverse Proxy
\n
Install Nginx Proxy Manager as a container and configure it to route your services to clean domain names like jellyfin.yourdomain.com. This also handles SSL certificates automatically via Let’s Encrypt, giving you HTTPS on all your services for free.
\n\n
Step 6: Add Storage and Expand
\n
Once your first service is stable, add a NAS or additional drives. Configure regular backups using the 3-2-1 rule: three copies of your data, on two different media types, with one copy stored off-site.
\n\n
The 5 Best Products for Every Self-Hosting Setup Ever
\n\n
1. Raspberry Pi 5 (4GB or 8GB)
\n
Specs: Broadcom BCM2712 quad-core ARM Cortex-A76 at 2.4GHz, 4GB or 8GB LPDDR4X RAM, PCIe 2.0 interface, dual 4K HDMI, USB 3.0, draws approximately 5 to 12 watts under load.
\n
Pros: Extremely low power consumption makes it ideal for 24/7 operation; large community with thousands of tutorials; compact enough to mount anywhere; PCIe slot enables NVMe SSD support for fast storage.
\n
Cons: Limited RAM ceiling means it struggles with more than four or five simultaneous Docker containers under heavy load.
\n
Best for: Absolute beginners who want to experiment with self-hosting without committing significant money.
\n
\n\n
2. HP EliteDesk 800 G3 Mini PC
\n
Specs: Intel Core i5-7500T quad-core at 2.7GHz (3.3GHz boost), typically 16GB DDR4 RAM, 256GB M.2 SSD, Intel HD Graphics 630, draws approximately 35 watts under typical load.
\n
Pros: Excellent performance-per-dollar ratio on the used market (often under $100); supports up to 32GB RAM; runs full x86 software without compatibility issues; quiet and compact.
\n
Cons: Older 7th-generation Intel platform means no support for newer virtualization features like nested virtualization in some edge cases.
\n
Best for: Beginners who want real x86 server performance without spending more than $150 total.
\n
\n\n
3. Synology DS223 2-Bay NAS
\n
Specs: Realtek RTD1619B quad-core 1.7GHz processor, 2GB DDR4 RAM, 2 drive bays supporting up to 36TB total with 2x 18TB drives, 1GbE LAN, draws approximately 18 watts with drives spinning.
\n
Pros: DiskStation Manager (DSM) software is the most beginner-friendly NAS interface available; built-in support for RAID 1 mirroring protects data if one drive fails; extensive app ecosystem including its own Synology Photos and Drive apps.
\n
Cons: Synology’s proprietary ecosystem can lock you in; the Realtek CPU is not powerful enough for 4K video transcoding.
\n
Best for: Beginners who want centralized home storage with a polished, easy-to-use interface and reliable data protection.
\n
\n\n
4. TP-Link TL-SG108E 8-Port Managed Switch
\n
Specs: 8x Gigabit Ethernet ports, VLAN support (802.1Q), QoS (Quality of Service) traffic prioritization, loop prevention, fanless design, draws approximately 6.1 watts maximum.
\n
Pros: Extremely affordable managed switch entry point; fanless operation means completely silent; VLAN support lets you isolate lab traffic from home devices; web-based management interface is straightforward for beginners.
\n
Cons: No PoE (Power over Ethernet) ports, so you cannot power access points or IP cameras directly from the switch.
\n
Best for: Any home lab that needs network segmentation and VLAN support without a significant budget investment.
\n
\n\n
5. APC Back-UPS 600VA UPS
\n
Specs: 600VA / 330W capacity, 7 battery backup outlets, automatic voltage regulation (AVR), USB connectivity for graceful server shutdown, runtime of approximately 17 minutes at half load.
\n
Pros: Protects all your hardware investment from power surges and outages; USB connection allows your server to automatically shut down safely before the battery dies; AVR corrects voltage fluctuations without switching to battery.
\n
Cons: 330W capacity is not sufficient for powering a full tower server plus NAS simultaneously; batteries require replacement every 3 to 5 years.
\n
Best for: Any home lab setup where data integrity and hardware protection matter — which is every setup, always.
\n
\n\n
Best Overall Pick: HP EliteDesk 800 G3 Mini PC
\n\n
If you could only buy one piece of hardware to start your self-hosting journey, the HP EliteDesk 800 G3 Mini PC wins without hesitation. Here is exactly why it beats every other option on this list for a beginner. First, the price-to-performance ratio is unmatched — you can find a fully loaded unit with 16GB RAM and a 256GB SSD for under $100 on the used market, which means you have budget left over for a NAS or a UPS. Second, it runs full x86 software, which means every single Docker image, every Linux distribution, and every self-hosting tutorial on the internet works on it without any ARM compatibility headaches. Third, it is genuinely quiet and compact enough to sit on a shelf without disturbing anyone in your home. In a real home lab setup, the EliteDesk 800 G3 handles a full stack of ten or more Docker containers — including Nextcloud, Jellyfin, Home Assistant, Nginx Proxy Manager, and Portainer — without breaking a sweat at typical home usage levels. It is the hardware equivalent of a reliable used car: not glamorous, but it just works.
\n\n
Full Comparison Table
\n\n
| Product | Type | CPU | RAM | Power Draw | Best For | Approx. Price |
|---|---|---|---|---|---|---|
| Raspberry Pi 5 | SBC Compute | Quad-core ARM 2.4GHz | 4GB / 8GB | 5–12W | Ultra-low power, experimentation | $60–$80 |
| HP EliteDesk 800 G3 | Mini PC Compute | Intel i5-7500T 2.7GHz | 16GB DDR4 | ~35W | Full x86 server on a budget | $80–$120 |
| Synology DS223 | 2-Bay NAS | Realtek 1.7GHz Quad | 2GB DDR4 | ~18W | Beginner NAS with RAID | $280–$320 |
| TP-Link TL-SG108E | Managed Switch | N/A | N/A | ~6W | VLAN segmentation, any lab | $25–$35 |
| APC Back-UPS 600VA | UPS | N/A | N/A | 330W max output | Hardware and data protection | $70–$90 |
\n\n
Common Mistakes Beginners Make
\n\n
Buying Too Much Hardware Too Soon
\n
The r/homelab community calls this \”rack acquisition syndrome\” — the irresistible urge to buy a full 12U rack, three servers, and a managed firewall before you have even run your first Docker container. What actually works in practice is starting with a single low-power device, getting comfortable with Linux and Docker, and only buying new hardware when you have a specific, justified need for it.
\n\n
Skipping Backups Entirely
\n
A RAID array is not a backup. RAID protects you from a single drive failure, but it does not protect you from accidental deletion, ransomware, or a house fire. Implement the 3-2-1 backup strategy from day one, even if your only off-site backup is a $10 USB drive at a family member’s house.
\n\n
Exposing Services Directly to the Internet
\n
Opening ports directly on your router and forwarding them to your home server is a common beginner move that creates serious security risks. Instead, use a Cloudflare Tunnel or a WireGuard VPN to access your services remotely without exposing any ports. This is one of the most important security habits you can build early. Learn more about setting up WireGuard VPN in your home lab.
\n\n
Ignoring Power Consumption
\n
Running an old enterprise server that draws 200 watts continuously will add roughly $175 to $200 to your annual electricity bill in the US. Always check the TDP and idle power draw of any device before committing to running it 24/7. See our guide on choosing a low-power home server for more detail.
\n\n
Not Documenting Anything
\n
Six months from now, you will have absolutely no memory of why you configured something a particular way. Keep a simple text file or a self-hosted wiki like BookStack documenting every service, every port, every configuration decision. Future you will be extremely grateful. Check out our home lab documentation tips for a simple system that actually sticks.
\n\n
Frequently Asked Questions
\n\n\n\n
What is the best hardware for a first self-hosting setup?
\n
For most beginners, a used mini PC like the HP EliteDesk 800 G3 is the best starting point. It offers full x86 compatibility, typically comes with 16GB RAM and a 256GB SSD, draws only about 35 watts, and can be found for under $120 on the used market. It runs every Docker container and Linux distribution without compatibility issues.
\n\n
How do I start self-hosting with no experience?
\n
Start by installing Ubuntu Server on a spare PC or a used mini PC, then install Docker and Portainer. Deploy a single useful service like Jellyfin or Nextcloud using a Docker Compose file from the official documentation. Get that one service stable and working before adding anything else. The most important thing is to start small and build confidence gradually.
\n\n
Do I need a NAS for self-hosting?
\n
You do not need a NAS to start self-hosting. A single USB hard drive or an internal drive in your compute device is perfectly fine for a first setup. A NAS becomes valuable when you need more than one or two terabytes of storage, want RAID redundancy to protect your data, or need multiple devices to access the same files simultaneously.
\n\n
What is the difference between a home lab and self-hosting?
\n
Self-hosting refers specifically to running your own versions of cloud services. A home lab is a broader term that includes self-hosting but also encompasses learning networking, virtualization, and systems administration. Most people who self-host consider themselves home lab enthusiasts, and the two communities overlap heavily on forums like r/selfhosted on Reddit.
\n\n
Conclusion
\n\n
Every selfhosting setup ever — from a single Raspberry Pi running one Docker container to a basement full of rack servers — started with someone who was confused, overwhelmed, and just decided to try anyway. The hardware recommendations in this guide will get you up and running without wasting money on gear you do not need yet, and the step-by-step walkthrough gives you a clear path from zero to a working setup. Remember: start with one service, get it stable, document what you did, and then expand. The home lab hobby rewards patience and curiosity more than it rewards spending money.
\n\n
Now it is your turn. What does your first self-hosting setup look like? Are you starting with a Raspberry Pi, a used mini PC, or something else entirely? Drop a comment below and share your build — the community here at HomeNode loves seeing beginner setups, and there is no such thing as a setup too small or too simple to be proud of. If you have questions about any of the hardware or software mentioned in this guide, ask them in the comments and we will do our best to help you get unstuck.
“,
“tags”: [“self-hosting”, “home lab”, “beginner guide”, “NAS”, “Docker”, “home server”, “networking”],
“meta_description”: “Discover every selfhosting setup ever in this complete beginner guide. Learn what hardware to buy, how to configure Docker, and build your first home lab for under $200.”,
“excerpt”: “Every self-hosting setup ever follows the same four-part pattern: compute, storage, networking, and software. This complete beginner guide walks you through each component, recommends the best budget hardware, and gives you a step-by-step walkthrough to get your first service running today.”,
“primary_keyword”: “every selfhosting setup ever”,
— Auburn AI editorial, Calgary AB